Skip to content

Conversation

@schultek
Copy link
Contributor

@schultek schultek commented Jan 13, 2026

Refactoring to cleaner Jaspr code for #12900

@schultek schultek requested review from a team and sfshaza2 as code owners January 13, 2026 13:57
@schultek schultek requested a review from ericwindmill January 13, 2026 13:57
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @schultek, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refactors the underlying architecture for how tutorial pages are rendered. By replacing a custom component with a page extension, the system centralizes the logic for structuring tutorial content, making the markdown files cleaner and more focused on content rather than presentation. This change improves maintainability and consistency across all tutorial pages.

Highlights

  • Tutorial Structure Refactoring: The previous TutorialLesson custom component has been removed and its functionality migrated to a new TutorialStructureExtension.
  • Content Simplification: All tutorial markdown files have been updated to remove explicit <TutorialLesson>, <TutorialIntro>, and <TutorialSteps> tags, relying instead on markdown --- dividers for structural parsing by the new extension.
  • New Page Extension: A TutorialStructureExtension has been introduced to programmatically apply the tutorial page layout (intro, steps, outro sections) based on markdown content and --- delimiters.
  • Stepper Component Update: The Stepper component now correctly uses the heading element for step titles, ensuring proper rendering of section headers.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@schultek schultek removed request for a team and sfshaza2 January 13, 2026 13:57
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request successfully refactors the tutorial structure from using a TutorialLesson custom component to a TutorialStructureExtension page extension. This change moves the logic for structuring tutorial pages into a dedicated extension, which processes the raw markdown content based on delimiters like ---. The TutorialLesson component and its related imports have been removed, and the markdown files have been updated to reflect the new structure by replacing custom tags with markdown dividers. The new extension correctly identifies and processes intro, steps, and trailing content, maintaining the intended layout and functionality of the tutorial pages. The changes align with the goal of cleaner Jaspr code by leveraging page extensions for content processing.

@flutter-website-bot
Copy link
Collaborator

flutter-website-bot commented Jan 13, 2026

Visit the preview URL for this PR (updated for commit d3516c6):

https://flutter-docs-prod--pr12923-ew-fwe-cleanup-2-0scopdyq.web.app

Copy link
Contributor

@ericwindmill ericwindmill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, Thank you!

@ericwindmill ericwindmill merged commit 8b39365 into ew-fwe-cleanup Jan 13, 2026
2 checks passed
@ericwindmill ericwindmill deleted the ew-fwe-cleanup-2 branch January 13, 2026 15:56
@schultek schultek mentioned this pull request Jan 13, 2026
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants